docs: plan from-scratch SIP stack - #40
Closed
wavekat-eason wants to merge 1 commit into
Closed
Conversation
Add plan doc 08 for a clean-room SIP transaction/dialog/transport engine that replaces the external stack dependency. Kept as an internal pub(crate) `stack` module inside the single `wavekat-sip` crate (no second crate), keeping `rsip` for message types and migrating flow-by-flow behind a patched-fork bridge. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BBYdYGwVkEUhUfeAAUoA3p
Contributor
Author
|
Already included in #43 (the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds plan doc 08 for a clean-room SIP transaction/dialog/transport engine that replaces the external SIP stack dependency over time.
Key decisions captured:
pub(crate)stackmodule insidewavekat-sip— consumers stillcargo add wavekat-sipand nothing else. De-leaking the engine from the public API is apubconcern, not a crate-boundary concern.rsipfor messages. Only the stateful layer (transactions, dialogs, transport, digest orchestration) is written from scratch — no reimplementing a SIP parser.[patch.crates-io]keeps calls working until each flow reaches parity — nothing big-bang.Why
ClientInviteDialogetc.), so even a version bump is a breaking change for consumers — and its current major line is a hard fork of its own message layer that still ships the bug.Scope of this PR
Documentation only — no code. Implementation starts at Phase 1 after sign-off on the plan.
🤖 Generated with Claude Code
https://claude.ai/code/session_01BBYdYGwVkEUhUfeAAUoA3p